home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
rbbs174.zip
/
174MSG.DOC
< prev
next >
Wrap
Text File
|
1992-06-23
|
3KB
|
70 lines
Version 17.4 of RBBS-PC optionally supports a new format of the
message file, in order to support carbon copy. There are only
two changes:
(a) byte 67 now contains the number of headers in the message.
For i = 1,2,3,...255, the character whose ascii value is i
is stored in that postion. E.g. a tab there means 9
headers, 1 header is the white smiley face. Hence there
is a maximum of 255 headers.
(b) there can be more than one header in the message, per byte
67. The difference between the headers reflects who the
message is TO. The same message can be to multiple people.
At the time the message is created, all the message headers
are identical except for
o who the message is to
Note that all the message headers have the same message #.
As the messages are read, two other fields may differ:
o the field marking when the message was received.
Each header is independently marked.
o the status byte of the message.
Each header can be independently killed.
Byte 67 of pre-17.4 message bases have a blank in byte 67, which
would ordinarily mean 32 header records. However, both RBBS-PC.EXE
and CONFIG.EXE are written with a "fail-safe" check to determine
whether the alleged record really is a header, and will correctly
read all message bases written by 17.4 and earlier versions. The
check employed is that true header records must have
o byte 116 must contain ascii value 225 or 226
If you want to be extra sure, you can also insist that
o bytes 70 and 73 must contain a "-" (part of date).
RBBS-PC works the following way with messages with multiple headers:
o the individual header is removed in a purge when it is marked as
killed and the count of the number of headers is reduced by one.
o the body of a message is not removed in a purge until all headers
are killed.
o if any header is to the person reading, that header controls the
access of the person. If that header is killed, for example,
the person can no longer read the message at all, unless the
person has sufficient security to read/kill all mail. If the
killed message is public, the person can read the message but
it will be treated as someone else's mail.
o when the caller says to kill a message, the caller can kill at most
the controlling header, unless the caller can read/kill all mail,
in which case the caller is individually asked to confirm the killing
of each header after being told the message number and who it is to
(though it would certainly be permissable to give the option to kill
all of them at once).
o "et al." is added to the display of the message header, at the end
of who the message is to, when the message is to more than one person.
The "et al." is NOT stored in the message header. Each person
the message is to sees the "et al." after their own name. "et al."
is Latin for "and others".